[PATCH 3/4] dnp3: set a bound on the number of points per message
authorJason Ish <jason.ish@oisf.net>
Wed, 7 Jan 2026 15:23:09 +0000 (09:23 -0600)
committerAndreas Dolp <dev@andreas-dolp.de>
Sun, 22 Feb 2026 12:28:52 +0000 (13:28 +0100)
commit2446137e3cb13e175d9056415cb086ae5e891254
tree9f8c7c28d72dd9060bc2013ff4cec24ddfb3142b
parent0a48413eddaf53884abd798b4f20b8de3ff9eb87
[PATCH 3/4] dnp3: set a bound on the number of points per message

16384 is used as the max, but a configuration parameter has been
provided. The reason for setting an upper bound is that bit flags can
create a memory amplification as we parse them into individual data
structures.

Ticket: #8181
(cherry picked from commit 3a32bb5743c35afb3278a6448f7e9669512dbe92)

Origin: upstream, https://github.com/OISF/suricata/commit/fdd79bdb14488244604729f1d68ca4bc60000dbd.patch
Bug: https://redmine.openinfosecfoundation.org/issues/8181
Subject: Upstream fix for CVE-2026-22259 part 3

Gbp-Pq: Name CVE-2026-22259_3.patch
doc/userguide/upgrade.rst
rules/dnp3-events.rules
src/app-layer-dnp3.c
src/app-layer-dnp3.h
suricata.yaml.in